Skip to content

[release-1.5] Cherry-pick JWT CVE fix into 1.5#2718

Merged
istio-testing merged 1 commit intoistio:release-1.5from
istio-testing:cherry-pick-2716-to-release-1.5
Feb 26, 2020
Merged

[release-1.5] Cherry-pick JWT CVE fix into 1.5#2718
istio-testing merged 1 commit intoistio:release-1.5from
istio-testing:cherry-pick-2716-to-release-1.5

Conversation

@istio-testing
Copy link
Collaborator

This is an automated cherry-pick of #2716


* Fixed JWT CVE related to exact PATH matches (istio#9)

* Fixed JWT CVE related to exact PATH matches

Problem: The JWT filter when matching exact paths included query parameters
which meant the JWT requirement could be bypassed by adding a "?" after the
path. The API was intended to only work for URIs.

Solution: The fix updates the match logic to only include URIs i.e. path
stripped off the query section.

Added unit tests to validate these cases.

* Fixed formatting

* Strip fragment of Path

Added unit tests to validate combination of query & fragment

* Fix lint

* Minor refactoring and more unit test cases (istio#11)

* Minor refactoring and more unit test cases

* Lint fixes

Signed-off-by: Yangmin Zhu <ymzhu@google.com>
@googlebot
Copy link
Collaborator

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added the cla: no Set by the Google CLA bot to indicate the author of a PR has not signed the Google CLA. label Feb 26, 2020
@istio-testing istio-testing added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 26, 2020
@yangminzhu yangminzhu added cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. and removed cla: no Set by the Google CLA bot to indicate the author of a PR has not signed the Google CLA. labels Feb 26, 2020
@googlebot
Copy link
Collaborator

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@yangminzhu
Copy link
Contributor

Manually set cla: yes as @nrjpoddar has committed the same change to other branches.

@yangminzhu yangminzhu changed the title [release-1.5] Cherry-pick JWT CVE fix into master [release-1.5] Cherry-pick JWT CVE fix into 1.5 Feb 26, 2020
@yangminzhu
Copy link
Contributor

@istio/release-managers-1-5 could you take a look? we should have cherry-picked this sooner after https://istio.io/news/releases/1.4.x/announcing-1.4.4/, need one more PR to update the proxy sha in istio. thanks.

@istio-testing istio-testing merged commit 637df71 into istio:release-1.5 Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants